-
Notifications
You must be signed in to change notification settings - Fork 77
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
Various bug fixes for heroku_app
resource
#257
Conversation
f0d1617
to
7707b4b
Compare
heroku_app
resource
7707b4b
to
71af60f
Compare
@davidji99 a bunch of acceptance tests failed already in Hashicorp CI, and the full run hasn't finished yet:
Most fail with:
I think this merits running tests locally to suss out the problems 😬 |
@mars, I did run some of the tests (I always do) locally but guess not enough of them. Thanks, back to the drawing board. |
723c65f
to
4f72eb3
Compare
|
@mars This is ready for review again. |
@davidji99 would you please rebase on master to get GitHub Action CI running on this branch? |
- change how team/org app is detected for the purpose of setting state attributes - move down Update() method - correctly set team/app attributes
b99dcf9
to
96d2979
Compare
@mars Done. ✅ Please review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wonderful fixes & updates here ✨ Thanks @davidji99
Resolves #249
Resolves #118
While looking into Imported heroku_app should include buildpacks #249, it didn't seem
heroku_app
's import function set ALL of the attributes of the app. So I changed this function to use the same read function as when creating/updating aheroku_app
.(EDIT: THIS change was undone) I also found it a good opportunity to change the value of
heroku_app.id
from the app's name to its UUID. We should always be prioritizing and using the resource's UUID whenever possible as the name is not idempotent. This shouldn't cause any major for users other than needing to reference theheroku_app.name
instead ofheroku_app.id
for a child resource such asheroku_addon.app_id
to avoid a destroy and recreate. Example state:Fix heroku_app in private space won't lock #118. I don't see how the
lock
attribute wouldn't be respected in aheroku_app
creation but nevertheless, I fixed how this attribute is set in state.I removed
heroku_app.uuid
. It should never have been an optional attribute and also redundant sinceheroku_app.id
is now set to its UUID.I did some basic refactoring in the
heroku_app
resource code.