Skip to content

Improve instance mapping guide #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lennardrother merged 3 commits into from
May 7, 2026
Merged

Improve instance mapping guide #100

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4cf486a
Add required role collection info
lennardrother May 6, 2026
e34d78d
Move verification to details block
lennardrother May 6, 2026
51ff726
Fix apiVersions in docs and examples
lennardrother May 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions docs/end-user-guides/instance-mapping.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,9 +186,14 @@ kubectl create -f cf-hana-instance-mapping.yaml

Your SAP HANA Cloud database is now mapped to the Cloud Foundry space and applications in that space can create HDI containers in your database.

If you [have a subscription to SAP HANA Cloud Administration Tools](/docs/crossplane-provider-btp/docs/end-user-guides/services/create-services#subscription), you can verify the creation of the instance mapping in the configuration of your SAP HANA Cloud instance:
<details>
<summary> Optional: Verify in SAP HANA Cloud Administration Tools</summary>

![Instance mapping in SAP HANA Cloud Administration Tools](/img/instance-mapping.png)
If you [have a subscription to SAP HANA Cloud Administration Tools](/docs/crossplane-provider-btp/docs/end-user-guides/services/create-services#subscription) and [assigned yourself](/docs/crossplane-provider-btp/docs/end-user-guides/account/usermanagement#assign-users-and-user-groups-to-role-collections-) the "SAP HANA Cloud Viewer" or "SAP HANA Cloud Administrator" role collection, you can verify the creation of the instance mapping in the configuration of your SAP HANA Cloud instance:

![Instance mapping in SAP HANA Cloud Administration Tools](/img/instance-mapping.png)

</details>

## Create an instance mapping (Kyma)

Expand Down
2 changes: 1 addition & 1 deletion docs/end-user-guides/setup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,7 +221,7 @@ data:
username: REJBRE1JTg== # E.g. Base64-encode: DBADMIN
password: Q2xvdWQtMTIzNDUh # Same password as set during service instance creation E.g. Base64-encode: Cloud-12345!
---
apiVersion: objects.hana.orchestrate.cloud.sap/v1alpha1
apiVersion: hana.sap.crossplane.io/v1alpha1
kind: ProviderConfig
metadata:
name: hana-providerconfig
Expand Down
6 changes: 3 additions & 3 deletions docs/end-user-guides/table.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ See [full CRD reference](https://github.com/SAP/crossplane-provider-hana/tree/ma
```

```yaml title="user.yaml"
apiVersion: admin.hana.orchestrate.cloud.sap/v1alpha1
apiVersion: admin.hana.sap.crossplane.io/v1alpha1
kind: User
metadata:
name: liquibase-user
Expand All @@ -78,7 +78,7 @@ See [full CRD reference](https://github.com/SAP/crossplane-provider-hana/tree/ma
Next, create the changelog schema and the managed schema:

```yaml title="changelog-schema.yaml"
apiVersion: objects.hana.orchestrate.cloud.sap/v1alpha1
apiVersion: schema.hana.sap.crossplane.io/v1alpha1
kind: DbSchema
metadata:
name: liquibase-changelog-schema
Expand All @@ -91,7 +91,7 @@ See [full CRD reference](https://github.com/SAP/crossplane-provider-hana/tree/ma
```

```yaml title="managed-schema.yaml"
apiVersion: schema.hana.orchestrate.cloud.sap/v1alpha1
apiVersion: schema.hana.sap.crossplane.io/v1alpha1
kind: DbSchema
metadata:
name: liquibase-changelog-schema
Expand Down
2 changes: 1 addition & 1 deletion docs/end-user-guides/users.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ See [full CRD reference](https://github.com/SAP/crossplane-provider-hana/tree/ma
We begin by provisioning a `User` resource.

```yaml title="user.yaml"
apiVersion: admin.hana.orchestrate.cloud.sap/v1alpha1
apiVersion: admin.hana.sap.crossplane.io/v1alpha1
kind: User
metadata:
name: my-orchestrated-user
Expand Down
2 changes: 1 addition & 1 deletion examples/instancemapping/kymainstancemapping-example.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ data:

---
# Step 2: ProviderConfig (placeholder - admin API credentials come from Kyma cluster)
apiVersion: hana.orchestrate.cloud.sap/v1alpha1
apiVersion: hana.sap.crossplane.io/v1alpha1
kind: ProviderConfig
metadata:
name: default
Expand Down
2 changes: 1 addition & 1 deletion examples/instancemapping/kymainstancemapping-local.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@

---
# Step 1: ProviderConfig (placeholder - admin API credentials come from ServiceBinding)
apiVersion: hana.orchestrate.cloud.sap/v1alpha1
apiVersion: hana.sap.crossplane.io/v1alpha1
kind: ProviderConfig
metadata:
name: default
Expand Down
2 changes: 1 addition & 1 deletion examples/instancemapping/providerconfig.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ stringData:
endpoint: abc123-456.hanacloud.ondemand.com
port: "443"
---
apiVersion: hana.orchestrate.cloud.sap/v1alpha1
apiVersion: hana.sap.crossplane.io/v1alpha1
kind: ProviderConfig
metadata:
name: default
Expand Down
Loading