@datarobot/pulumi-datarobot 0.11.0 → 0.11.2

package/artifact.d.ts

@@ -37,7 +37,7 @@ export declare class Artifact extends pulumi.CustomResource {
      */
     readonly name: pulumi.Output<string>;
     /**
-     * Local source directory to upload to the DataRobot catalog and attach to the primary container's `image_build_config.code_ref`. When source content changes, the provider uploads, triggers an image build on the draft artifact, and (by default) waits for completion before proceeding. On draft artifacts, uploads are applied in-place. On locked artifacts, source changes clone to a new draft version, upload, build, patch <span pulumi-lang-nodejs="`codeRef`" pulumi-lang-dotnet="`CodeRef`" pulumi-lang-go="`codeRef`" pulumi-lang-python="`code_ref`" pulumi-lang-yaml="`codeRef`" pulumi-lang-java="`codeRef`" pulumi-lang-hcl="`code_ref`">`codeRef`</span>, and lock the new version.
+     * Local source directory to synchronize with the DataRobot catalog and attach to the primary container's `image_build_config.code_ref`. When source content changes, the provider syncs, triggers an image build on the draft artifact, and (by default) waits for completion before proceeding. On draft artifacts, uploads are applied in-place. On locked artifacts, source changes clone to a new draft version, upload, build, patch <span pulumi-lang-nodejs="`codeRef`" pulumi-lang-dotnet="`CodeRef`" pulumi-lang-go="`codeRef`" pulumi-lang-python="`code_ref`" pulumi-lang-yaml="`codeRef`" pulumi-lang-java="`codeRef`" pulumi-lang-hcl="`code_ref`">`codeRef`</span>, and lock the new version. **Apply writes to <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span>:** the sync is three-way (last-synced state vs. local files vs. catalog), the same algorithm the DataRobot CLI uses, so besides uploading local changes it also keeps bookkeeping under `dir/.datarobot/workload/` (last-synced manifest, catalog pointers and lock file; the directory carries its own `.gitignore`), downloads files that exist in the catalog but not locally, and removes local files that were deleted from the catalog, reporting each as a warning. A file changed on both sides since the last sync (edited or deleted locally, and edited or deleted in the catalog) fails the apply before anything is uploaded or written, because `pulumi up` cannot ask which side wins; resolve it in that directory with the DataRobot CLI (`dr artifact code sync`) and apply again. When the artifact's catalog version moved since the directory last synced (the CLI synced the artifact from another checkout, or this resource was last applied from one), the plan shows <span pulumi-lang-nodejs="`dirHash`" pulumi-lang-dotnet="`DirHash`" pulumi-lang-go="`dirHash`" pulumi-lang-python="`dir_hash`" pulumi-lang-yaml="`dirHash`" pulumi-lang-java="`dirHash`" pulumi-lang-hcl="`dir_hash`">`dirHash`</span> as known after apply and apply brings the catalog's changes down. A directory can back only one <span pulumi-lang-nodejs="`datarobot.Artifact`" pulumi-lang-dotnet="`datarobot.Artifact`" pulumi-lang-go="`Artifact`" pulumi-lang-python="`Artifact`" pulumi-lang-yaml="`datarobot.Artifact`" pulumi-lang-java="`datarobot.Artifact`" pulumi-lang-hcl="`datarobot_artifact`">`datarobot.Artifact`</span> resource: its sync state is bound to that resource's catalog, so a second resource over a directory that already backs a live artifact from another artifact repository is refused. `.datarobot.yaml` is never uploaded.
      */
     readonly source: pulumi.Output<outputs.ArtifactSource | undefined>;
     /**
@@ -82,7 +82,7 @@ export interface ArtifactState {
      */
     name?: pulumi.Input<string | undefined>;
     /**
-     * Local source directory to upload to the DataRobot catalog and attach to the primary container's `image_build_config.code_ref`. When source content changes, the provider uploads, triggers an image build on the draft artifact, and (by default) waits for completion before proceeding. On draft artifacts, uploads are applied in-place. On locked artifacts, source changes clone to a new draft version, upload, build, patch <span pulumi-lang-nodejs="`codeRef`" pulumi-lang-dotnet="`CodeRef`" pulumi-lang-go="`codeRef`" pulumi-lang-python="`code_ref`" pulumi-lang-yaml="`codeRef`" pulumi-lang-java="`codeRef`" pulumi-lang-hcl="`code_ref`">`codeRef`</span>, and lock the new version.
+     * Local source directory to synchronize with the DataRobot catalog and attach to the primary container's `image_build_config.code_ref`. When source content changes, the provider syncs, triggers an image build on the draft artifact, and (by default) waits for completion before proceeding. On draft artifacts, uploads are applied in-place. On locked artifacts, source changes clone to a new draft version, upload, build, patch <span pulumi-lang-nodejs="`codeRef`" pulumi-lang-dotnet="`CodeRef`" pulumi-lang-go="`codeRef`" pulumi-lang-python="`code_ref`" pulumi-lang-yaml="`codeRef`" pulumi-lang-java="`codeRef`" pulumi-lang-hcl="`code_ref`">`codeRef`</span>, and lock the new version. **Apply writes to <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span>:** the sync is three-way (last-synced state vs. local files vs. catalog), the same algorithm the DataRobot CLI uses, so besides uploading local changes it also keeps bookkeeping under `dir/.datarobot/workload/` (last-synced manifest, catalog pointers and lock file; the directory carries its own `.gitignore`), downloads files that exist in the catalog but not locally, and removes local files that were deleted from the catalog, reporting each as a warning. A file changed on both sides since the last sync (edited or deleted locally, and edited or deleted in the catalog) fails the apply before anything is uploaded or written, because `pulumi up` cannot ask which side wins; resolve it in that directory with the DataRobot CLI (`dr artifact code sync`) and apply again. When the artifact's catalog version moved since the directory last synced (the CLI synced the artifact from another checkout, or this resource was last applied from one), the plan shows <span pulumi-lang-nodejs="`dirHash`" pulumi-lang-dotnet="`DirHash`" pulumi-lang-go="`dirHash`" pulumi-lang-python="`dir_hash`" pulumi-lang-yaml="`dirHash`" pulumi-lang-java="`dirHash`" pulumi-lang-hcl="`dir_hash`">`dirHash`</span> as known after apply and apply brings the catalog's changes down. A directory can back only one <span pulumi-lang-nodejs="`datarobot.Artifact`" pulumi-lang-dotnet="`datarobot.Artifact`" pulumi-lang-go="`Artifact`" pulumi-lang-python="`Artifact`" pulumi-lang-yaml="`datarobot.Artifact`" pulumi-lang-java="`datarobot.Artifact`" pulumi-lang-hcl="`datarobot_artifact`">`datarobot.Artifact`</span> resource: its sync state is bound to that resource's catalog, so a second resource over a directory that already backs a live artifact from another artifact repository is refused. `.datarobot.yaml` is never uploaded.
      */
     source?: pulumi.Input<inputs.ArtifactSource | undefined>;
     /**
@@ -115,7 +115,7 @@ export interface ArtifactArgs {
      */
     name?: pulumi.Input<string | undefined>;
     /**
-     * Local source directory to upload to the DataRobot catalog and attach to the primary container's `image_build_config.code_ref`. When source content changes, the provider uploads, triggers an image build on the draft artifact, and (by default) waits for completion before proceeding. On draft artifacts, uploads are applied in-place. On locked artifacts, source changes clone to a new draft version, upload, build, patch <span pulumi-lang-nodejs="`codeRef`" pulumi-lang-dotnet="`CodeRef`" pulumi-lang-go="`codeRef`" pulumi-lang-python="`code_ref`" pulumi-lang-yaml="`codeRef`" pulumi-lang-java="`codeRef`" pulumi-lang-hcl="`code_ref`">`codeRef`</span>, and lock the new version.
+     * Local source directory to synchronize with the DataRobot catalog and attach to the primary container's `image_build_config.code_ref`. When source content changes, the provider syncs, triggers an image build on the draft artifact, and (by default) waits for completion before proceeding. On draft artifacts, uploads are applied in-place. On locked artifacts, source changes clone to a new draft version, upload, build, patch <span pulumi-lang-nodejs="`codeRef`" pulumi-lang-dotnet="`CodeRef`" pulumi-lang-go="`codeRef`" pulumi-lang-python="`code_ref`" pulumi-lang-yaml="`codeRef`" pulumi-lang-java="`codeRef`" pulumi-lang-hcl="`code_ref`">`codeRef`</span>, and lock the new version. **Apply writes to <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span>:** the sync is three-way (last-synced state vs. local files vs. catalog), the same algorithm the DataRobot CLI uses, so besides uploading local changes it also keeps bookkeeping under `dir/.datarobot/workload/` (last-synced manifest, catalog pointers and lock file; the directory carries its own `.gitignore`), downloads files that exist in the catalog but not locally, and removes local files that were deleted from the catalog, reporting each as a warning. A file changed on both sides since the last sync (edited or deleted locally, and edited or deleted in the catalog) fails the apply before anything is uploaded or written, because `pulumi up` cannot ask which side wins; resolve it in that directory with the DataRobot CLI (`dr artifact code sync`) and apply again. When the artifact's catalog version moved since the directory last synced (the CLI synced the artifact from another checkout, or this resource was last applied from one), the plan shows <span pulumi-lang-nodejs="`dirHash`" pulumi-lang-dotnet="`DirHash`" pulumi-lang-go="`dirHash`" pulumi-lang-python="`dir_hash`" pulumi-lang-yaml="`dirHash`" pulumi-lang-java="`dirHash`" pulumi-lang-hcl="`dir_hash`">`dirHash`</span> as known after apply and apply brings the catalog's changes down. A directory can back only one <span pulumi-lang-nodejs="`datarobot.Artifact`" pulumi-lang-dotnet="`datarobot.Artifact`" pulumi-lang-go="`Artifact`" pulumi-lang-python="`Artifact`" pulumi-lang-yaml="`datarobot.Artifact`" pulumi-lang-java="`datarobot.Artifact`" pulumi-lang-hcl="`datarobot_artifact`">`datarobot.Artifact`</span> resource: its sync state is bound to that resource's catalog, so a second resource over a directory that already backs a live artifact from another artifact repository is refused. `.datarobot.yaml` is never uploaded.
      */
     source?: pulumi.Input<inputs.ArtifactSource | undefined>;
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@datarobot/pulumi-datarobot",
-    "version": "0.11.0",
+    "version": "0.11.2",
     "description": "A Pulumi package for creating and managing DataRobot resources.",
     "keywords": [
         "datarobot",

package/types/input.d.ts

@@ -74,15 +74,15 @@ export interface ApplicationSourceRuntimeParameterValue {
 }
 export interface ArtifactSource {
     /**
-     * Path to the local directory containing application source files to upload.
+     * Path to the local directory containing application source files to synchronize. Apply may add, overwrite, or remove files in this directory, and keeps sync state under `dir/.datarobot/workload/`, so the directory must be writable; see the <span pulumi-lang-nodejs="`source`" pulumi-lang-dotnet="`Source`" pulumi-lang-go="`source`" pulumi-lang-python="`source`" pulumi-lang-yaml="`source`" pulumi-lang-java="`source`" pulumi-lang-hcl="`source`">`source`</span> description.
      */
     dir: pulumi.Input<string>;
     /**
-     * SHA-256 fingerprint of uploadable files under <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span> after `.drignore` / system excludes. Used to detect changes and skip re-upload when unchanged. Files covered by a system exclude are never part of this hash.
+     * SHA-256 fingerprint of uploadable files under <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span> after `.drignore` / system excludes. Used to detect changes and skip the sync when unchanged. Files covered by a system exclude, including the sync state directory, are never part of this hash. When the directory differs from state, or the catalog moved since the directory last synced, it plans as known after apply, because the sync may add or remove files under <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span>; the value recorded is the digest of the directory once the sync is done.
      */
     dirHash?: pulumi.Input<string | undefined>;
     /**
-     * When <span pulumi-lang-nodejs="`true`" pulumi-lang-dotnet="`True`" pulumi-lang-go="`true`" pulumi-lang-python="`true`" pulumi-lang-yaml="`true`" pulumi-lang-java="`true`" pulumi-lang-hcl="`true`">`true`</span> (default), if <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span> has neither `.drignore` nor `.wapiignore`, the provider writes a default `.drignore` at the start of apply. Existing ignore files are never overwritten. Set to <span pulumi-lang-nodejs="`false`" pulumi-lang-dotnet="`False`" pulumi-lang-go="`false`" pulumi-lang-python="`false`" pulumi-lang-yaml="`false`" pulumi-lang-java="`false`" pulumi-lang-hcl="`false`">`false`</span> to skip autogeneration. System excludes always apply and cannot be re-enabled from `.drignore`: `.datarobot.yaml`, `.git`, `.gitignore`, `.wapi`, `.datarobot/workload`, and Terraform's own `.terraform`, `terraform.tfstate*` and `*.tfvars` files.
+     * When <span pulumi-lang-nodejs="`true`" pulumi-lang-dotnet="`True`" pulumi-lang-go="`true`" pulumi-lang-python="`true`" pulumi-lang-yaml="`true`" pulumi-lang-java="`true`" pulumi-lang-hcl="`true`">`true`</span> (default), if <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span> has neither `.drignore` nor `.wapiignore`, the provider writes a default `.drignore` at the start of apply. Existing ignore files are never overwritten. Set to <span pulumi-lang-nodejs="`false`" pulumi-lang-dotnet="`False`" pulumi-lang-go="`false`" pulumi-lang-python="`false`" pulumi-lang-yaml="`false`" pulumi-lang-java="`false`" pulumi-lang-hcl="`false`">`false`</span> to skip autogeneration. System excludes always apply and cannot be re-enabled from `.drignore`: `.datarobot.yaml`, `.git`, `.gitignore`, `.wapi`, `.datarobot/workload`, the `<path>.LOCAL.<timestamp>` copies the DataRobot CLI's sync keeps, and Terraform's own `.terraform`, `terraform.tfstate*` and `*.tfvars` files.
      */
     generateIgnore?: pulumi.Input<boolean | undefined>;
     /**

package/types/output.d.ts

@@ -73,15 +73,15 @@ export interface ApplicationSourceRuntimeParameterValue {
 }
 export interface ArtifactSource {
     /**
-     * Path to the local directory containing application source files to upload.
+     * Path to the local directory containing application source files to synchronize. Apply may add, overwrite, or remove files in this directory, and keeps sync state under `dir/.datarobot/workload/`, so the directory must be writable; see the <span pulumi-lang-nodejs="`source`" pulumi-lang-dotnet="`Source`" pulumi-lang-go="`source`" pulumi-lang-python="`source`" pulumi-lang-yaml="`source`" pulumi-lang-java="`source`" pulumi-lang-hcl="`source`">`source`</span> description.
      */
     dir: string;
     /**
-     * SHA-256 fingerprint of uploadable files under <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span> after `.drignore` / system excludes. Used to detect changes and skip re-upload when unchanged. Files covered by a system exclude are never part of this hash.
+     * SHA-256 fingerprint of uploadable files under <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span> after `.drignore` / system excludes. Used to detect changes and skip the sync when unchanged. Files covered by a system exclude, including the sync state directory, are never part of this hash. When the directory differs from state, or the catalog moved since the directory last synced, it plans as known after apply, because the sync may add or remove files under <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span>; the value recorded is the digest of the directory once the sync is done.
      */
     dirHash: string;
     /**
-     * When <span pulumi-lang-nodejs="`true`" pulumi-lang-dotnet="`True`" pulumi-lang-go="`true`" pulumi-lang-python="`true`" pulumi-lang-yaml="`true`" pulumi-lang-java="`true`" pulumi-lang-hcl="`true`">`true`</span> (default), if <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span> has neither `.drignore` nor `.wapiignore`, the provider writes a default `.drignore` at the start of apply. Existing ignore files are never overwritten. Set to <span pulumi-lang-nodejs="`false`" pulumi-lang-dotnet="`False`" pulumi-lang-go="`false`" pulumi-lang-python="`false`" pulumi-lang-yaml="`false`" pulumi-lang-java="`false`" pulumi-lang-hcl="`false`">`false`</span> to skip autogeneration. System excludes always apply and cannot be re-enabled from `.drignore`: `.datarobot.yaml`, `.git`, `.gitignore`, `.wapi`, `.datarobot/workload`, and Terraform's own `.terraform`, `terraform.tfstate*` and `*.tfvars` files.
+     * When <span pulumi-lang-nodejs="`true`" pulumi-lang-dotnet="`True`" pulumi-lang-go="`true`" pulumi-lang-python="`true`" pulumi-lang-yaml="`true`" pulumi-lang-java="`true`" pulumi-lang-hcl="`true`">`true`</span> (default), if <span pulumi-lang-nodejs="`dir`" pulumi-lang-dotnet="`Dir`" pulumi-lang-go="`dir`" pulumi-lang-python="`dir`" pulumi-lang-yaml="`dir`" pulumi-lang-java="`dir`" pulumi-lang-hcl="`dir`">`dir`</span> has neither `.drignore` nor `.wapiignore`, the provider writes a default `.drignore` at the start of apply. Existing ignore files are never overwritten. Set to <span pulumi-lang-nodejs="`false`" pulumi-lang-dotnet="`False`" pulumi-lang-go="`false`" pulumi-lang-python="`false`" pulumi-lang-yaml="`false`" pulumi-lang-java="`false`" pulumi-lang-hcl="`false`">`false`</span> to skip autogeneration. System excludes always apply and cannot be re-enabled from `.drignore`: `.datarobot.yaml`, `.git`, `.gitignore`, `.wapi`, `.datarobot/workload`, the `<path>.LOCAL.<timestamp>` copies the DataRobot CLI's sync keeps, and Terraform's own `.terraform`, `terraform.tfstate*` and `*.tfvars` files.
      */
     generateIgnore: boolean;
     /**