Part of [Service provider auctions for web deployments](https://www.notion.so/Service-provider-auctions-for-web-deployments-104a6b22d47280dbad51d28aa3a91d75)
- Use deployer API to get status of the deployments
Co-authored-by: Shreerang Kale <shreerangkale@gmail.com>
Co-authored-by: IshaVenikar <ishavenikar7@gmail.com>
Co-authored-by: Adw8 <adwaitgharpure@gmail.com>
Reviewed-on: #15
Co-authored-by: Nabarun Gogoi <nabarun@deepstacksoft.com>
Co-committed-by: Nabarun Gogoi <nabarun@deepstacksoft.com>
### TL;DR
Update references to the new GitHub repository URLs and make minor formatting fixes in deployment scripts.
### What changed?
Updated GitHub repository URLs from `snowball-tools-platform` to `snowball-tools` in various deployment and test scripts. Made minor formatting adjustments including spacing and indentation.
### How to test?
Run the deployment scripts in their respective environments to ensure they reference the correct repository URLs and all functionalities work as expected. Check for successful creation and updation of application records.
### Why make this change?
This change was made to reflect the new repository structure and ensure consistency across all deployment scripts. The minor formatting fixes improve code readability.
---
* Fetch latest registry record version and increment
* Move reference up
* Remove steps to manually update record values
* Update registry config with new key and bond
* feat: one click deployer
This adds a script for deploying whatever is the latest on main, essentially automating the changes specified in the readme.
* fix
* repurpose existing script
* clean up
* fix
* fix
* Update latest record version
---------
Co-authored-by: Nabarun <nabarun@deepstacksoft.com>
* Add script and records for deploying frontend app
* Update readme with steps for new deployment
* Add troubleshooting section
* Move config env update
* Add step to commit updated records
* Bump record version
