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

Please add a charm action to run the upload_assets console command #209

Closed
barryprice opened this issue Mar 31, 2024 · 3 comments
Closed
Assignees

Comments

@barryprice
Copy link
Contributor

Enhancement Proposal

Hi

It's possible for a charmed deploy using S3 integration to enter a state where the generated HTML references S3-hosted files that don't exist - see #208.

Currently the least painful workaround is to get a discourse console session on a pod, and run bundle exec rails s3:upload_assets.

This enhancement proposal is a request for a charm action to perform the above, and ideally to confirm a successful upload.

@cbartz
Copy link
Contributor

cbartz commented Nov 6, 2024

@javierdelapuente Please have a look and create a ticket in the backlog if necessary.

@javierdelapuente
Copy link
Contributor

Hi @barryprice, IINM, currently the pods gets into error state if the migration fails. As the redis bug should be fixed by now, I do not think a new action should be necessary.

If this is still happening with the latest version of the charm, please inform us so we can investigate it.

Thanks.

@cbartz
Copy link
Contributor

cbartz commented Nov 15, 2024

Closing, @barryprice , please comment if this is still necessary.

@cbartz cbartz closed this as completed Nov 15, 2024
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

3 participants