alkiranet / terraform-provider-alkira

Alkira Terraform Provider

Terraform Provider for Alkira

• Website: http://www.alkira.com

The Terraform provider for Alkira is a Terraform plugin to enable full lifecycle management of Alkira resources. The provider is maintained internally by Alkira engineering team.

Currently, the provider is still in early development phase and being actively worked on.

Getting Started

To start using the provider, you will need Terraform 1.0 or above.

Development Requirements

• Terraform Latest Release
• Go 1.20.x (to build the provider plugin on all architectures, especially Apple M1)

terraform-provider-alkira's Issues

Error while installing alkiranet/alkira v0.9.5: checksum list has no SHA-256 hash for "terraform-provider-alkira_0.9.5_windows_amd64.zip

@spikewang , @SpaSmALX @mac-alkira
I am trying to do terraform init for alkira , but i am facing this error.

terraform {
required_providers {
alkira = {
source = "alkiranet/alkira"
version = "0.9.5"
}
}
}

provider "alkira" {
portal = "your_tenant_name.portal.alkira.com"
username = "[email protected]"
password = "your_password"
}

alkira_connector_azure_vnet

According to examples in https://registry.terraform.io/providers/alkiranet/alkira/latest/docs/resources/connector_azure_vnet, the credential_id is alkira_credential_azure_vnet.id, but in this sample repo, it's alkira_credential.id:
https://github.com/alkiranet/terraform-alkira-connector-azure/blob/main/main.tf#L37.

Please clarify whether it's alkira_credential_azure_vnet or alkira_credential?

alkira_connector_remote_access (Resource) doesn't accept prefixes.

Hi,
I'm using Terraform to deploy a remote_access resource following this documentation https://registry.terraform.io/providers/alkiranet/alkira/latest/docs/resources/connector_remote_access.

Seems that it is possible to enable split_tunneling but there is no option in the schema to set the prefix list.