-
Notifications
You must be signed in to change notification settings - Fork 639
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
fix(front50-gcs): Fix ObjectType filenames for GCS Front50 persistent store #1493
Conversation
What's involved in adding a test to prevent this bug in the future? |
Let me see what we have here. Probably simulate a GCS bucket with existing objects (application, serviceaccounts, projects etc) and filenames specification.json. And retrieving them in a test. @dbyron-sf automatically closed by the merge? |
Yeah, github is too smart...I re-opened. |
841c21c
to
d2be063
Compare
@dbyron-sf Added some tests to cover all types loading |
Thank you! |
@Mergifyio backport release-1.34.x release-1.35.x |
✅ Backports have been created
|
https://github.com/Mergifyio backport release-1.32.x release-1.33.x |
✅ Backports have been created
|
By fixing the GCS to SQL migration in this PR and removing the hardcoded "specification.json" from the GCSStorageService i cause an issue with all ObjectTypes except the Application and ApplicationPermission.
More specifically the offending change is this one which had an effect in all the other ObjectTypes in GCS to get/store the filenames defined in the ObjectType and not the previously used
specification.json
for GCS.Fixes issue spinnaker/spinnaker#6970