Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate set up and deployment to tag-based approach #78

Open
ebma opened this issue Nov 15, 2024 · 1 comment
Open

Migrate set up and deployment to tag-based approach #78

ebma opened this issue Nov 15, 2024 · 1 comment

Comments

@ebma
Copy link
Member

ebma commented Nov 15, 2024

Context

Subsquid introduced a new system to manage deployments. Instead of using version numbers and having a single production deployment, they want to use tags for each deployment. More info here.

Since the configuration we use currently, with designated production deployments, is deprecated and might be removed in the future, we should change our setup to support the tag based approach.

TODO

  • Adjust the parameters in each manifest file
  • Change the instructions of the README to describe how to publish new versions to production
  • Make sure that other integrations are aware of the new tag-based endpoints. These integrations are Zenlink and the Pendulum portal.
@ebma
Copy link
Member Author

ebma commented Nov 15, 2024

@pendulum-chain/product this is a nice-to-have feature that might become important sooner or later. It's unclear when subsquid will stop supporting our current setup so the squids might break in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant