Open ytsarev opened 1 year ago
For reproduction.
The problematic source sample was
⚠ apiVersion: cache.aws.crossplane.io/v1alpha1
kind: CacheCluster
metadata:
name: test
spec:
forProvider:
region: us-east-1
applyImmediately: true
engine: memcached
cacheNodeType: cache.t2.micro
numCacheNodes: 1
engineVersion: 6.2
cacheParameterGroupName: test
port: 6379
cacheSubnetGroupName: test
preferredMaintenanceWindow: mon:02:20-mon:03:20
securityGroupIDRefs:
- name: test-memcached-security-group
writeConnectionSecretToRef:
name: test-memcached-creds
namespace: test
providerConfigRef:
name: awsconfig
The 'fixed' source sample is
⚠ apiVersion: cache.aws.crossplane.io/v1alpha1
kind: CacheCluster
metadata:
name: test
spec:
forProvider:
region: us-east-1
applyImmediately: true
engine: memcached
cacheNodeType: cache.t2.micro
numCacheNodes: 1
engineVersion: "6.2"
cacheParameterGroupName: test
port: 6379
cacheSubnetGroupName: test
preferredMaintenanceWindow: mon:02:20-mon:03:20
securityGroupIDRefs:
- name: test-memcached-security-group
writeConnectionSecretToRef:
name: test-memcached-creds
namespace: test
providerConfigRef:
name: awsconfig
So it was engineVersion: 6.2
vs engineVersion: "6.2"
that was introducing the failure
What problem are you facing?
Currently while working on migrator and having some bug in the source sample, I am getting
It is not clear where it is happening
How could Upjet help solve your problem?
Increase error verbosity, provide some context and hints around the place of failure