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

Provider Attribute form modification #194

Open
baktun14 opened this issue May 14, 2024 · 0 comments
Open

Provider Attribute form modification #194

baktun14 opened this issue May 14, 2024 · 0 comments
Labels
P1 priority 1 feature/ enhancement

Comments

@baktun14
Copy link
Collaborator

baktun14 commented May 14, 2024

The issue:

  • When providers edit their attributes on Cloudmos/Console, it properly writes the new attributes on chain. However, when they update their providers with helm, it updates the attributes again, but with the values set in their local environment in the provider.yaml.

Solution:

  • Instead of getting rid of the form to have one source of truth, we can instead of signing a transaction to update the provider attributes, provide the instructions on how to update their provider.yaml file with the generated portion for the attributes.
@baktun14 baktun14 added the P2 priority 2 feature/ enhancement label May 14, 2024
@baktun14 baktun14 added P1 priority 1 feature/ enhancement and removed P2 priority 2 feature/ enhancement labels Jun 3, 2024
@baktun14 baktun14 changed the title Provider Attribute form Provider Attribute form modification Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 priority 1 feature/ enhancement
Projects
Status: Up Next (prioritized)
Development

No branches or pull requests

1 participant