An Oracle Cloud (OCI) Pulumi resource package, providing multi-language access to OCI

Oracle Cloud Infrastructure Resource Provider

The Oracle Cloud Infrastructure (OCI) Resource Provider lets you manage OCI resources.

Installing

This package is available for several languages/platforms:

Node.js (JavaScript/TypeScript)

To use with JavaScript or TypeScript in Node.js, install using either npm:

npm install @pulumi/oci

or yarn:

yarn add @pulumi/oci

Python

To use with Python, install using pip:

python3 -m pip install pulumi_oci

Go

To use with Go, use go get to grab the latest version of the library:

go get github.com/pulumi/pulumi-oci/sdk/...

.NET

To use with .NET, install using dotnet add package:

dotnet add package Pulumi.Oci

Configuration

The following configuration options are available for the oci provider:

Option Environment variable Description
oci:tenancyOcid TF_VAR_tenancy_ocid OCID of your tenancy.
oci:userOcid TF_VAR_user_ocid OCID of the user calling the API.
oci:privateKey TF_VAR_private_key The contents of the private key file. Required if privateKeyPath is not defined and takes precedence if both are defined.
oci:privateKeyPath TF_VAR_private_key_path The path (including filename) of the private key stored on your computer. Required if privateKey is not defined.
oci:privateKeyPassword TF_VAR_private_key_password Passphrase used for the key, if it is encrypted.
oci:fingerprint TF_VAR_fingerprint Fingerprint for the key pair being used.
oci:region TF_VAR_region An OCI region.
oci:configFileProfile TF_VAR_config_file_profile The custom profile to use instead of the DEFAULT profile in .oci/config.

Use the Required Keys and OCIDs chapter of the OCI Developer Guide to learn:

Reference

For detailed reference documentation, please visit the Pulumi registry.

Comments
  • Rename to pulumi-oracle-cloud

    Rename to pulumi-oracle-cloud

    Iโ€™m worried that reserving the oci name for Oracle Cloud means weโ€™d need a really random name for a provider that builds OCI artifacts.

    https://github.com/opencontainers/artifacts

    Container images are now OCI images and within the Cloud Native space, weโ€™re seeing a lot of new patterns emerging that are built on top of OCI too.

    I know Terraform call this OCI, but this is a really random name from Oracle - especially as members of the Open Container Initiative.

  • Not able to remove resources

    Not able to remove resources

    What happened?

    Using python, even the command "pulumi down" come back with resource delete successfully, the OCI resources remain in OCI without removal at all.

    image

    Steps to reproduce

    • Python 3.9.6
    • pulumi_oci==0.1.1
    • pulumi == 3.33.2

    -- Create resources with "pulumi up" with simple python like below import pulumi import pulumi_oci as oci oci.identity.Compartment("Test",compartment_id="ocid1.compartment.oc1.xxxxxxxxxxxxxxxxx",description="This is a test")

    -- Destroy resources with "pulumi down"

    Expected Behavior

    Provisioned resources in OCI be removed after pulumi down report success

    Actual Behavior

    Provisioned resources in OCI still available (even after days, so it's not a time lag problem) after pulumi down reported success.

    Versions used

    NAME VERSION pip 22.1 pulumi-oci 0.1.1 setuptools 62.2.0 wheel 0.37.1

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • SecurityList related types are missing in Go

    SecurityList related types are missing in Go

    What happened?

    I am unable to add either IngressSecurityRules or EngressSecurityRules when creating a SecurityList using the Go SDK. At least the following types are not defined:

    • SecurityListEgressSecurityRuleArray
    • SecurityListEgressSecurityRuleArgs
    • SecurityListIngressSecurityRuleArray
    • SecurityListIngressSecurityRuleArgs

    Steps to reproduce

    Using

    github.com/pulumi/pulumi-oci/sdk  0.5.0
    github.com/pulumi/pulumi/sdk/v3   3.44.2
    

    Create a compartment and VCN, then try to create a SecurityList

    Create a new security list as follows

    name := "test-security-list"
    _, err := core.NewSecurityList(ctx, name, &core.SecurityListArgs{
    		CompartmentId: compartment.ID()
    		VcnId:         vcn.ID(),
    		DisplayName:   pulumi.String(name),
    		EgressSecurityRules: core.SecurityListEgressSecurityRuleArray{
    			core.SecurityListEgressSecurityRuleArgs{
    				Protocol:    pulumi.String("all"),
    				Destination: pulumi.String("0.0.0.0/0"),
    			},
    		},
    })
    

    Expected Behavior

    Should be able to use types

    • SecurityListEgressSecurityRuleArray
    • SecurityListEgressSecurityRuleArgs
    • SecurityListIngressSecurityRuleArray
    • SecurityListIngressSecurityRuleArgs

    Actual Behavior

    Unresolved type 'SecurityListEgressSecurityRuleArray'
    

    Output of pulumi about

    CLI          
    Version      3.50.1
    Go Version   go1.19.4
    Go Compiler  gc
    
    Plugins
    NAME  VERSION
    go    unknown
    oci   0.5.0
    
    Host     
    OS       darwin
    Version  12.5
    Arch     arm64
    
    This project is written in go: executable='/usr/local/go/bin/go' version='go version go1.19.1 darwin/amd64'
    
    Dependencies:
    NAME                              VERSION
    github.com/pulumi/pulumi-oci/sdk  0.5.0
    github.com/pulumi/pulumi/sdk/v3   3.44.2
    

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • [Documentation] Get Service documentation is not correct

    [Documentation] Get Service documentation is not correct

    What happened?

    Following the documentation -https://www.pulumi.com/registry/packages/oci/api-docs/core/getservices/ is getting an d error as there is no module called 'Core'

    Steps to reproduce

    import pulumi
    import pulumi_oci as oci
    
    test_services = oci.Core.get_services()
    

    its a typo ,it should be 'core'

    Expected Behavior

    List all the services

    Actual Behavior

    No module called Core , its a typo ,it should be 'core'

    Versions used

    NA

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • [Import Failure] No module - container_engine

    [Import Failure] No module - container_engine

    What happened?

    Did a pulumi import of oke and got the resource definition as below

                                                            compartment_id=config.get('compartment_ocid'),
                                                            endpoint_config=oci.container.engine.ClusterEndpointConfigArgs(
                                                                is_public_ip_enabled=config.get('oke_is_public_ip_enabled'),
                                                                subnet_id="ocid1.subnet.oc1.iad.aaaaaaa
    

    while applying back got an error

     pulumi:pulumi:Stack (pulumi-python-oci-devops-oke-oci-devops-oke):
        OKE Cluster creation failed module 'pulumi_oci' has no attribute 'container_engine'
     
        error: preview failed
     
    
    
    

    Steps to reproduce

    rahulmr_in@rahulmr_in-mac pulumi_oci_devops % pulumi import oci:ContainerEngine/cluster:Cluster test_cluster "ID"

    Expected Behavior

    Import should work for further actions too, and in the oci lib there is no module called container_engine but it is container engine

    Actual Behavior

    OKE import is as below ...

    test_cluster = oci.container_engine.Cluster("test_cluster", compartment_id="ocid1.compartment.oc1..aaaaaaaalmc42p5bsqbfo5jkle7uy7bwnlazr7ghw26qorsidrwbl6mk6xva", endpoint_config=oci.container.engine.ClusterEndpointConfigArgs(

    Versions used

    CLI
    Version 3.33.2 Go Version go1.17.10 Go Compiler gc

    Plugins NAME VERSION oci 0.1.1 python unknown

    Host
    OS darwin Version 11.6.3 Arch x86_64

    This project is written in python (/usr/bin/python3 v3.8.9)

    Current Stack: oci-devops-oke

    TYPE URN pulumi:pulumi:Stack urn:pulumi:oci-devops-oke::pulumi-python-oci-devops-oke::pulumi:pulumi:Stack::pulumi-python-oci-devops-oke-oci-devops-oke pulumi:providers:oci urn:pulumi:oci-devops-oke::pulumi-python-oci-devops-oke::pulumi:providers:oci::default_0_1_1 oci:ContainerEngine/cluster:Cluster urn:pulumi:oci-devops-oke::pulumi-python-oci-devops-oke::oci:ContainerEngine/cluster:Cluster::test_cluster oci:Core/vcn:Vcn urn:pulumi:oci-devops-oke::pulumi-python-oci-devops-oke::oci:Core/vcn:Vcn::test_vcn

    Found no pending operations associated with oci-devops-oke

    Backend
    Name pulumi.com URL https://app.pulumi.com/RahulMR42 User RahulMR42 Organizations RahulMR42

    NAME VERSION pip 22.1.1 pulumi-oci 0.1.1 setuptools 62.3.2 wheel 0.37.1

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • Invalid reference to module

    Invalid reference to module "ContainerEngine"

    What happened?

    import pulumi
    import pulumi_oci as oci
    
    test_cluster_kube_config = oci.ContainerEngine.get_cluster_kube_config(cluster_id=oci_containerengine_cluster["test_cluster"]["id"], <== Invalid ContainerEngine
        endpoint=var["cluster_kube_config_endpoint"],
        expiration=var["cluster_kube_config_expiration"],
        token_version=var["cluster_kube_config_token_version"])
    

    Steps to reproduce

    https://www.pulumi.com/registry/packages/oci/api-docs/containerengine/getclusterkubeconfig/

    Expected Behavior

    Proper doc

    Actual Behavior

    Invalid module 'pulumi_oci' has no attribute 'ContainerEngine'

    Versions used

    NA

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • Oci deployment stage import failing

    Oci deployment stage import failing

    What happened?

    Imported code snippet is invalid

    deployto_oke = oci.dev_ops.DeployStage("deployto_oke", < Invalid module dev.ops or dev_ops
        deploy_pipeline_id="ocid1.devopsdeploypipeline.oc1.iad.xxx",
        deploy_stage_predecessor_collection=oci.dev.ops.DeployStageDeployStagePredecessorCollectionArgs(
            items=[oci.dev.ops.DeployStageDeployStagePredecessorCollectionItemArgs(
                id="ocid1.devopsdeploypipeline.oc1.iad.xxx",
            )],
        ),
        deploy_stage_type="OKE_DEPLOYMENT",
        description="Apply asdasd",
        display_name="Apply",
        kubernetes_manifest_deploy_artifact_ids=["ocid1.devopsdeployartifact.oc1.iad.xxx"],
        namespace="default",
        oke_cluster_deploy_environment_id="ocid1.devopsdeployenvironment.oc1.iad.xxx",
        rollback_policy=oci.dev.ops.DeployStageRollbackPolicyArgs(
            policy_type="AUTOMATED_STAGE_ROLLBACK_POLICY",
        ))
    
    

    Steps to reproduce

    pulumi import oci:DevOps/deployStage:DeployStage test_deploy_stage "id"

    Expected Behavior

    Code should be usable as is .

    Actual Behavior

    Invalid module ,must be devops.

    Versions used

    NA

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • OCI Deploymentpipeline import is failing

    OCI Deploymentpipeline import is failing

    What happened?

    Tried importing the OCI Deploypipeline ,the imported pipeline code snippet is not having the correct module informations.

    ocidevops_pipeline = oci.dev_ops.DeployPipeline("ocidevops_pipeline", < ===Invalid module dev_ops or dev.ops
        deploy_pipeline_parameters=oci.dev.ops.DeployPipelineDeployPipelineParametersArgs(
            items=[oci.dev.ops.DeployPipelineDeployPipelineParametersItemArgs(
                default_value="ns-node",
                description="A namespace for the deployment",
                name="namespace",
            )],
        ),
        description="Pipeline to deploy to OKE using devops and pulumi",
        display_name="pulumi_devops_deploypipeline",
        project_id="ocid1.devopsproject.oc1.iad.xx")
    

    Steps to reproduce

    pulumi import oci:DevOps/deployPipeline:DeployPipeline test_deploy_pipeline "id"

    Expected Behavior

    Imported definition code should be usable

    Actual Behavior

    Invalid module dev_ops or dev.ops

    Versions used

    NA

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • OCI Pulumi invalid module Objectstorage

    OCI Pulumi invalid module Objectstorage

    What happened?

    'pulumi_oci' has no attribute 'ObjectStorage' when using it with oci.Objectstorage

    The valid module should be objectstorage

    Steps to reproduce

    import pulumi
    import pulumi_oci as oci
    
    test_namespace = oci.ObjectStorage.get_namespace(compartment_id=var["compartment_id"])
    

    Expected Behavior

    Should return the namespace

    Actual Behavior

    Failing the execution ,invalid module ObjectStorage

    Versions used

    na

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • Deploy artifact import is not correct

    Deploy artifact import is not correct

    What happened?

    Did a pulumi import of deploy artifact and its not correct on the format and build param.

    artifact_containerrepo = oci.dev_ops.DeployArtifact("artifact_containerrepo", < == Invalid module name dev_ops or dev.ops
        argument_substitution_mode="SUBSTITUTE_PLACEHOLDERS",
        deploy_artifact_source=oci.dev.ops.DeployArtifactDeployArtifactSourceArgs(
            deploy_artifact_source_type="OCIR",
            image_uri=f"us-ashburn-1.ocir.io/fahdabidiroottenancy/mr_devops_pulumi_oke_repo:{buildru_n__hash}", <==The values is not correct its actually BUILDRUN_HASH 
        ),
        deploy_artifact_type="DOCKER_IMAGE",
        display_name="pulumi_devops_containerrepo_artifact",
        project_id="ocid1.devopsproject.oc1.iad.xxx")
    
    

    Steps to reproduce

    pulumi import oci:DevOps/deployArtifact:DeployArtifact test_deploy_artifact "id"

    Expected Behavior

    Imported modules should be able to use as it

    • module name should beDevOpss
    • parametertosubstitutee must be as defined in the actual artifact
    image

    Actual Behavior

    code snippet is not correct.

    Versions used

    na

    Additional context

    Its a pulumi-terraform bridge issue

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • Devops build stage is not working as expected .

    Devops build stage is not working as expected .

    What happened?

    build_stage_appbuild = oci.dev_ops.BuildPipelineStage("build_stage_appbuild",
        build_pipeline_id="ocid1.devopsbuildpipeline.oc1.iad.xxxx",
        build_pipeline_stage_predecessor_collection=oci.dev.ops.BuildPipelineStageBuildPipelineStagePredecessorCollectionArgs(
            items=[oci.dev.ops.BuildPipelineStageBuildPipelineStagePredecessorCollectionItemArgs(
                id="ocid1.devopsbuildpipeline.oc1.iad.xxxx",
            )],
        ),
        build_pipeline_stage_type="BUILD",
        build_source_collection=oci.dev.ops.BuildPipelineStageBuildSourceCollectionArgs(
            items=[oci.dev.ops.BuildPipelineStageBuildSourceCollectionItemArgs(
                branch="main",
                connection_type="DEVOPS_CODE_REPOSITORY",
                name="node_express",
                repository_id="ocid1.devopsrepository.oc1.iad.xxx",
                repository_url="https://devops.scmservice.us-ashburn-1.oci.oraclecloud.com/namespaces/"
            )],
        ),
        description="Build your application.",
        display_name="BuildStage",
        image="OL7_X86_64_STANDARD_10",
        primary_build_source="node_express",
        stage_execution_timeout_in_seconds=36000)
    
    

    The code generated are wrong , there are no modules like dev_ops or dev.ops must be devops

    Steps to reproduce

    pulumi import oci:DevOps/buildPipelineStage:BuildPipelineStage test_build_pipeline_stage "id"

    Expected Behavior

    Should be able to use exported code as is .

    Actual Behavior

    Wrong devops module.

    Versions used

    na

    Additional context

    Its a terraform - pulumi bridge issue.

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • Resources don't seem to be adding resource name when created

    Resources don't seem to be adding resource name when created

    What happened?

    Creating OCI resources doesn't appear to be adding the pulumi resource name

    Steps to reproduce

    Create any resource, for example a VCN

    vcn = new oci.core.Vcn(
          "example",
          {
            compartmentId: <someid>,
            cidrBlocks: [<someCidr>],
            
          },
      );
    

    Expected Behavior

    I would expect the resulting vcn to be called something like example-<randomstring>

    Actual Behavior

    It creates a vcn with a set name:

    vcn<randomstring>
    

    Output of pulumi about

    No response

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

  • Leaking debug messages

    Leaking debug messages

    What happened?

    When you try provision something that takes longer than a few seconds, the provider leaks debug message.

    Steps to reproduce

    Define something like an OKE resource.

    Expected Behavior

    You don't get any debug/info messages

    Actual Behavior

    You get this:

    
    
        pulumi:pulumi:Stack ts_oke-dev running
        jaxxstorm:index:OciVcn example
        oci:Core:Vcn example
        oci:Core:InternetGateway example
     +  oci:Core:SecurityList example creating
        oci:Core:NatGateway example
        oci:Core:Subnet example-private-1
        oci:Core:Subnet example-public-1
     +  oci:Core:RouteTable example creating
     +  oci:ContainerEngine:Cluster example creating
        oci:Core:ServiceGateway example
     +  oci:Core:RouteTable example creating
     +  oci:Core:SecurityList example created
     +  oci:Core:RouteTable example created
     +  oci:Core:RouteTable example created
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 09:58:37.375682 Time elapsed for retry: 0s;  Expected retry duration: 0s
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 09:58:38.905261 Time elapsed for retry: 2s;  Expected retry duration: 0s
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 09:58:46.646189 Time elapsed for retry: 9s;  Expected retry duration: 0s
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 09:58:50.889506 Time elapsed for retry: 14s;  Expected retry duration: 0s
    @ Updating....
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 09:59:06.856503 Time elapsed for retry: 30s;  Expected retry duration: 0s
    @ Updating....
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 09:59:30.194056 Time elapsed for retry: 53s;  Expected retry duration: 0s
    @ Updating....
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 09:59:43.144472 Time elapsed for retry: 1m6s;  Expected retry duration: 0s
    @ Updating.......
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 10:01:04.001465 Time elapsed for retry: 2m27s;  Expected retry duration: 0s
    @ Updating......
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 10:01:54.754863 Time elapsed for retry: 3m17s;  Expected retry duration: 0s
    @ Updating.......
        pulumi:pulumi:Stack ts_oke-dev running INFO 2022/10/12 10:03:23.189656 Time elapsed for retry: 4m46s;  Expected retry duration: 0s
    @ Updating.............
     +  oci:ContainerEngine:Cluster example created
        pulumi:pulumi:Stack ts_oke-dev  10 messages
    
    Diagnostics:
      pulumi:pulumi:Stack (ts_oke-dev):
        INFO 2022/10/12 09:58:37.375682 Time elapsed for retry: 0s;  Expected retry duration: 0s
        INFO 2022/10/12 09:58:38.905261 Time elapsed for retry: 2s;  Expected retry duration: 0s
        INFO 2022/10/12 09:58:46.646189 Time elapsed for retry: 9s;  Expected retry duration: 0s
        INFO 2022/10/12 09:58:50.889506 Time elapsed for retry: 14s;  Expected retry duration: 0s
        INFO 2022/10/12 09:59:06.856503 Time elapsed for retry: 30s;  Expected retry duration: 0s
        INFO 2022/10/12 09:59:30.194056 Time elapsed for retry: 53s;  Expected retry duration: 0s
        INFO 2022/10/12 09:59:43.144472 Time elapsed for retry: 1m6s;  Expected retry duration: 0s
        INFO 2022/10/12 10:01:04.001465 Time elapsed for retry: 2m27s;  Expected retry duration: 0s
        INFO 2022/10/12 10:01:54.754863 Time elapsed for retry: 3m17s;  Expected retry duration: 0s
        INFO 2022/10/12 10:03:23.189656 Time elapsed for retry: 4m46s;  Expected retry duration: 0s
    

    Output of pulumi about

    No response

    Additional context

    No response

    Contributing

    Vote on this issue by adding a ๐Ÿ‘ reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

The OCI Service Operator for Kubernetes (OSOK) makes it easy to connect and manage OCI services from a cloud native application running in a Kubernetes environment.

OCI Service Operator for Kubernetes Introduction The OCI Service Operator for Kubernetes (OSOK) makes it easy to create, manage, and connect to Oracle

Sep 27, 2022
The Oracle Database Operator for Kubernetes (a.k.a. OraOperator) helps developers, DBAs, DevOps and GitOps teams reduce the time and complexity of deploying and managing Oracle Databases

The Oracle Database Operator for Kubernetes (a.k.a. OraOperator) helps developers, DBAs, DevOps and GitOps teams reduce the time and complexity of deploying and managing Oracle Databases. It eliminates the dependency on a human operator or administrator for the majority of database operations.

Dec 14, 2022
Injective-price-oracle-ext - Injective's Oracle with dynamic price feeds (for External Integrations)

injective-price-oracle Injective's Oracle with dynamic price feeds. Allows anyon

Aug 29, 2022
Fadvisor(FinOps Advisor) is a collection of exporters which collect cloud resource pricing and billing data guided by FinOps, insight cost allocation for containers and kubernetes resource
Fadvisor(FinOps Advisor) is a collection of exporters which collect cloud resource pricing and billing data guided by FinOps, insight cost allocation for containers and kubernetes resource

[TOC] Fadvisor: FinOps Advisor fadvisor(finops advisor) is used to solve the FinOps Observalibility, it can be integrated with Crane to help users to

Jan 3, 2023
Pulumi-tencentcloud - Pulumi provider for tencentcloud

Terraform Bridge Provider Boilerplate This repository contains boilerplate code

Dec 30, 2021
Pulumi-awscontroltower - A Pulumi provider for AWS Control Tower

Terraform Bridge Provider Boilerplate This repository contains boilerplate code

Nov 14, 2022
Go-gke-pulumi - A simple example that deploys a GKE cluster and an application to the cluster using pulumi

This example deploys a Google Cloud Platform (GCP) Google Kubernetes Engine (GKE) cluster and an application to it

Jan 25, 2022
Pulumi-k8s-operator-example - OpenGitOps Compliant Pulumi Kubernetes Operator Example

Pulumi GitOps Example OpenGitOps Compliant Pulumi Kubernetes Operator Example Pr

May 6, 2022
Terraform Provider for Azure (Resource Manager)Terraform Provider for Azure (Resource Manager)
Terraform Provider for Azure (Resource Manager)Terraform Provider for Azure (Resource Manager)

Terraform Provider for Azure (Resource Manager) Version 2.x of the AzureRM Provider requires Terraform 0.12.x and later, but 1.0 is recommended. Terra

Oct 16, 2021
Apachedist-resource - A concourse resource to track updates of an apache distribution, e.g. tomcat

Apache Distribution Resource A concourse resource that can track information abo

Feb 2, 2022
Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration
Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration

Karmada Karmada: Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration Karmada (Kubernetes Armada) is a Kubernetes management system that enables

Dec 30, 2022
provide api for cloud service like aliyun, aws, google cloud, tencent cloud, huawei cloud and so on

cloud-fitter ไบ‘้€‚้… Communicate with public and private clouds conveniently by a set of apis. ็”จไธ€ๅฅ—ๆŽฅๅฃ๏ผŒไพฟๆทๅœฐ่ฎฟ้—ฎๅ„็ฑปๅ…ฌๆœ‰ไบ‘ๅ’Œ็งๆœ‰ไบ‘ ๅฏนๆŽฅ่ฎกๅˆ’ ๅ†…้ƒจ็ญนๅค‡ไธญ๏ผŒๅŽ็ปญๅผ€ๆ”พ๏ผŒๆœ‰้œ€ๆฑ‚ๆฌข่ฟŽ่”็ณปใ€‚ ๅผ€ๅ‘่€…็คพๅŒบ ๅผ€ๅ‘่€…็คพๅŒบๆ–‡ๆกฃ

Dec 20, 2022
Pulumi provider for the Elasticsearch Service and Elastic Cloud Enterprise

Terraform Bridge Provider Boilerplate This repository contains boilerplate code for building a new Pulumi provider which wraps an existing Terraform p

Nov 18, 2022
Crane (FinOps Crane) is an opensource project which manages cloud resource on Kubernetes stack, it is inspired by FinOps concepts.
Crane (FinOps Crane) is an opensource project which manages cloud resource on Kubernetes stack, it is inspired by FinOps concepts.

Crane (FinOps Crane) is an opensource project which manages cloud resource on Kubernetes stack, it is inspired by FinOps concepts. Goal of Crane is to provide an one-stop shop project to help Kubernetes users to save cloud resource usage with a rich set of functionalities.

Jan 3, 2023
Go WhatsApp Multi-Device Implementation in REST API with Multi-Session/Account Support

Go WhatsApp Multi-Device Implementation in REST API This repository contains example of implementation go.mau.fi/whatsmeow package with Multi-Session/

Dec 3, 2022
Cloud-Z gathers information and perform benchmarks on cloud instances in multiple cloud providers.

Cloud-Z Cloud-Z gathers information and perform benchmarks on cloud instances in multiple cloud providers. Cloud type, instance id, and type CPU infor

Jun 8, 2022
OCI Image Encryption Package

imgcrypt image encryption library and command line tool Project imgcrypt is a non-core subproject of containerd. The imgcrypt library provides API exe

Jan 5, 2023
A Go package providing a generic data type to track maximum and minimum peak values.

go-peak Overview go-peak is a Go package providing a generic data type that tracks the maximum and minimum peak values within a specific period of tim

Mar 26, 2022
๐Ÿšข Go package providing lifecycle management for PostgreSQL Docker instances.
๐Ÿšข  Go package providing lifecycle management for PostgreSQL Docker instances.

?? psqldocker powered by ory/dockertest. Go package providing lifecycle management for PostgreSQL Docker instances. Leverage Docker to run unit and in

Sep 2, 2022