ripe-gigabyte-88964
09/20/2023, 1:03 PMAddress
relative to another address? E.g. if I have address path/to/my/address:target_a
and string :target_b
how can I generate the address path/to/my/address:target_b
?ripe-gigabyte-88964
09/20/2023, 1:50 PMawait Get
?curved-television-6568
09/20/2023, 2:25 PMripe-gigabyte-88964
09/20/2023, 2:26 PMdef _resolver(self, spec: str) -> Address:
address_input = AddressInput.parse(
spec=spec,
description_of_origin="",
relative_to=self._root_address
)
return Address(
address_input.path_component,
target_name=address_input.target_component,
generated_name=address_input.generated_component,
parameters=address_input.parameters
)
curved-television-6568
09/20/2023, 2:27 PMself._root_address
a path?curved-television-6568
09/20/2023, 2:28 PMself._root_address.spec_path
ripe-gigabyte-88964
09/20/2023, 2:28 PMcurved-television-6568
09/20/2023, 2:29 PMAddressInput
has file_to_address
and dir_to_address
.. sure they don’t do what you want instead of creating the Address
manually?ripe-gigabyte-88964
09/20/2023, 2:31 PMfile_to_address
work with helm deployments? Because I know these addresses are going to either refer to a helm deployment, docker image, or another custom target type that doesn't have a sources component.ripe-gigabyte-88964
09/20/2023, 2:31 PMBUILD
file?curved-television-6568
09/20/2023, 2:32 PMripe-gigabyte-88964
09/20/2023, 2:32 PMcurved-television-6568
09/20/2023, 2:33 PMcurved-television-6568
09/20/2023, 2:33 PMcurved-television-6568
09/20/2023, 2:37 PM