There is a problem with the provider where if an existing pipeline that uses a template is imported to state and then updated, it returns a Unable to update Pipeline: input: Custom step configuration is not permitted, instead it is derived from the associated pipeline template
This is because it skips over the plan modifier because its an existing pipeline, and then tries to set the steps to an empty string in the graphql mutation. This likely instead needs to set the steps as null or just not include them in the mutation so that the API does not try to deal with a template and defined steps
There is a problem with the provider where if an existing pipeline that uses a template is imported to state and then updated, it returns a
Unable to update Pipeline: input: Custom step configuration is not permitted, instead it is derived from the associated pipeline templateThis is because it skips over the plan modifier because its an existing pipeline, and then tries to set the steps to an empty string in the graphql mutation. This likely instead needs to set the steps as null or just not include them in the mutation so that the API does not try to deal with a template and defined steps