-
Notifications
You must be signed in to change notification settings - Fork 7
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
[BUG] Changing controller instance type doesn't cause cluster to be update #202
Comments
This is because the config file is now a jinja template that is stored in s3 and a custom resource expands the template and store the resolved template in s3. So the stack now doesn't see the parallel cluster config as an input to anything, just the path to the s3 object. Update the custom resource to output the hash of config file and put that as an input the the parallelcluster custom resource. |
cartalla
added a commit
that referenced
this issue
Feb 26, 2024
Move the code that expands the config file template to a separate lambda and custom resource so we can get its sha512 hash and use it to determine when the cluster needs to be updated. Resolves #202
cartalla
added a commit
that referenced
this issue
Feb 26, 2024
Move the code that expands the config file template to a separate lambda and custom resource so we can get its sha512 hash and use it to determine when the cluster needs to be updated. Resolves #202
cartalla
added a commit
that referenced
this issue
Feb 26, 2024
Move the code that expands the config file template to a separate lambda and custom resource so we can get its sha512 hash and use it to determine when the cluster needs to be updated. Resolves #202
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I changed /slurm/SlurmCtl/instance_type and updated the config stack and CDK doesn't detect any stack changes.
The text was updated successfully, but these errors were encountered: