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

Documentation: Adding new keys in storage_directive #522

Open
hemanthnakkina opened this issue Jul 11, 2024 · 0 comments
Open

Documentation: Adding new keys in storage_directive #522

hemanthnakkina opened this issue Jul 11, 2024 · 0 comments
Labels
hint/good-first-issue a small bug good for newcomers hint/main going on main branch kind/doc indicates a documentation change

Comments

@hemanthnakkina
Copy link
Contributor

hemanthnakkina commented Jul 11, 2024

Description

The documentation says Adding a new key/value pair will add storage to the application on upgrade.

Applied a terraform plan.
Add new key/value pair to storage_directive. No changes from this step as expected.
Change channel of the application. Upgrade triggered but the new key/value pair is not observed on the deployed application.

@anvial clarified that Upgrade will affect only from charm rev with no storage to charm rev with storage support.
This bug is more to clarify this as part of documentation.

Urgency

Casually reporting

Terraform Juju Provider version

0.13.0-rc1

Terraform version

1.9.1

Juju version

3.4.2

Terraform Configuration(s)

NA

Reproduce / Test

NA

Debug/Panic Output

No response

Notes & References

No response

@hmlanigan hmlanigan added kind/doc indicates a documentation change hint/main going on main branch labels Jul 18, 2024
@hmlanigan hmlanigan added the hint/good-first-issue a small bug good for newcomers label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hint/good-first-issue a small bug good for newcomers hint/main going on main branch kind/doc indicates a documentation change
Projects
None yet
Development

No branches or pull requests

2 participants