SAP Tech Bytes is an initiative to bring you bite-sized information on all manner of topics, in video and written format. If you’re still using SAPCP_CLIENTCONFIG, don’t worry – there’s a grace period the btp CLI will still honour the use of this environment variable, to give you time to change over to BTP_CLIENTCONFIG. That’s my personal choice, and I use the BTP_CLIENTCONFIG environment variable to tell the btp CLI that this is where I have my configuration: Moving over Note that my btp CLI configuration directory is not hidden, i.e. configstore/ gcloud/ kitty/ ranger/ vim/Īutocomplete/ exercism/ gitui/ newsboat/ stack/ yamllint/ This is what the contents of my $HOME/.config/ directory looks like: ls. btp/ directory name means that it is to be treated as a hidden directory). $HOME/.config/) according to the name of the tool or utility, but as normal directories, rather than hidden ones (the period at the start of the. My configuration locationĪs I mentioned in the SAP Tech Bytes: btp CLI – managing configuration post, I like to organise my configuration directories within my XDG_CONFIG_HOME location (i.e. It is now BTP_CLIENTCONFIG, which reflects the current name of the btp CLI of course. This reflected the name of the btp CLI at the time ( sapcp). config/, but also the environment variable that you can set to tell the btp CLI where your configuration is, has changed too. Not only has the default location changed from. But, if you installed tmuxinator via Ruby's gem, you'll need to run the following commands to put the completion files where they'll be loaded by your shell. This is a great move because it aligns with the XDG Base Directory Specification which I mentioned in the previous post. Your distribution's package manager may install the completion files in the appropriate location for the completion to load automatically on startup. (here you can see examples of other files alongside config.json). 19:30, Remove tmux pane split command, Anders Damsgaard, 1, +0, -1. So for me, while working in my local dev container, would have been, previously: # /home/user One way to do it is to use tmux templating library like tmuxinator. profile: dont add the same dir to path more than once. In the past, the default location for this. There are sometimes other files that contain configuration too, and these, along with config.json, are stored by default in a directory called. The main btp CLI configuration is stored in a file called config.json. This is also what the getbtpcli script reports (see SAP Tech Bytes: btp CLI – installation for more on this utility): getbtpcli -test This is independent of your runtime environment while the previous post showed an example in the SAP Business Application Studio (App Studio), this update applies to all contexts where you run the latest version of the btp CLI.Īt the time of writing, according to the information in the canonical home for the btp CLI, the latest version of the btp CLI is 2.14.0: One of these updates has been to where configuration is stored (and looked for) by default. Since that post, the btp CLI has gone through a number of updates. This post relates directly to the SAP Tech Bytes: btp CLI – managing configuration post, and provides a brief update to the information in there. Be informed about updates to where the btp CLI configuration is stored by default.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |