Hi, where is the best place to report an issue wit...
# esc
f
Hi, where is the best place to report an issue with ESC in the web UI, specifically the table view? The issue we have is that our pulumi config has period in the namespace and it is fine everywhere except when someone edits the environment in the table view, the dots are read as yaml mappings inside the
pulumiConfig
section and we end up with our config values nested which breaks the next deployment.
r
Hi! You can open an issue here - we're aware of some bugs in the table view and are in the process of collecting feedback to inform our investment here - curious if you'd be open to chatting more about your usage of the table view.
f
Thanks, will do. I do not use the tableview as I prefer the explicitness of the YAML but I have had users in our infrequently have to update values that are source values that are mapped into the config keys in
pulumiConfig
and the table view will convert those keys into YAML mappings. eg (trivial example):
Copy code
values:
  my-app:
    db-password:
      fn::secret:
        ciphertext: some-ciphertext
  pulumiConfig:
    pendula.app.my-app:db-password: ${my-app.db-password}
will get turned into:
Copy code
values:
  my-app:
    db-password:
      fn::secret:
        ciphertext: some-new-ciphertext
  pulumiConfig:
    pendula:
      app:
        my-app:db-password: ${my-app.db-password}
and then we wonder who unset db-password the app (and probably all the other variables)
Thanks for the quick reply btw 🙂