feat(automations): datasource support #310
Conversation
|
|
||
| //nolint:paralleltest // we use the resource.ParallelTest helper instead | ||
| func TestAccDatasource_automation(t *testing.T) { | ||
| eventTriggerAutomationResourceName := testutils.NewRandomPrefixedString() |
There was a problem hiding this comment.
(no changes required) something I forgot to mention in the Resource PR: because we're using ephemeral workspaces, I don't believe we need the resource names to be random
There was a problem hiding this comment.
hmm - i thought they had to be unique (even across test cases) so that they wouldn't overwrite the resource in the TF state. i know this is the datasource test, but if we were in the resource test and used the same names, wouldn't they perform an Update()?
There was a problem hiding this comment.
Fair, I may be writing tests slightly with different expectations - I assume each test case is updating an existing resource so I can test Update functionality. Sounds like it may just be a different use case?
resolves https://linear.app/prefect/issue/PLA-577/tfp-automations-scaffold-datasource
followup to #305