Git Product home page Git Product logo

Comments (2)

mpayne-coveo avatar mpayne-coveo commented on May 24, 2024

I second this. This would be very useful for us to have as well.

from terraform-provider-prefect.

carlosjourdan avatar carlosjourdan commented on May 24, 2024

We started using the provider very early in a client, and a lot of features were still unsupported. We have very little experience with golang and terraform, but were able to fork the repository and implement a couple of resources and datasources.

Now we have an outdated version, and it seems that it would be a good strategy to switch back to the official provider. One of the main gaps that we're still seeing is provider support.

So we're considering creating a PR to merge our code. This is what our resource model looks like:

type DeploymentResourceModel struct {
	ID          customtypes.UUIDValue      `tfsdk:"id"`
	Created     customtypes.TimestampValue `tfsdk:"created"`
	Updated     customtypes.TimestampValue `tfsdk:"updated"`
	AccountID   customtypes.UUIDValue      `tfsdk:"account_id"`
	WorkspaceID customtypes.UUIDValue      `tfsdk:"workspace_id"`

	Name                       types.String          `tfsdk:"name"`
	FlowID                     customtypes.UUIDValue `tfsdk:"flow_id"`
	InfrastructureBlockID      customtypes.UUIDValue `tfsdk:"infrastructure_block_id"`
	StorageBlockID             customtypes.UUIDValue `tfsdk:"storage_block_id"`
	Path                       types.String          `tfsdk:"path"`
	EntryPoint                 types.String          `tfsdk:"entrypoint"`
	WorkPoolName               types.String          `tfsdk:"work_pool_name"`
	WorkQueueName              types.String          `tfsdk:"work_queue_name"`
	ParameterOpenApiSchemaJson jsontypes.Normalized `tfsdk:"parameters_openapi_schema_json"`
	ParametersJson             jsontypes.Normalized `tfsdk:"parameters_json"`
	ScheduleJson               jsontypes.Normalized `tfsdk:"schedule_json"`
	IsScheduleActive           types.Bool            `tfsdk:"is_schedule_active"`
}

We took a shortcut by using jsontypes in some complex fields that maybe could be better modeled. The decision to add the "_json" suffix to those fields was to allow for backwards compatibility in case they were properly implemented as nested attributes. Is that something that could fly on the main codebase?

from terraform-provider-prefect.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.