Cloud developer roadmap updates

abap-developer-roadmap/Development Tools/X.1 Development Tools.md

@@ -2,9 +2,9 @@
 In the SAP world, there is the old and the new world of development tools.
 
 
-More and more familiar tools are being used. Eclipse plays a central role in ABAP development and Build Code in cloud development. This helps non-SAP developers to familiarise themselves with the processes more quickly. Especially the ABAP Development Tools allow developers to manage connections to multiple systems, customize their development experience to their specific needs and increase their productivity. Plugins for the development environment, such as ABAP Cleaner and Code Pal, are only possible in ADT.
+More and more familiar tools are being used. Eclipse plays a central role in ABAP development, VS Code is becoming an additional option, and Build Code is important in cloud development. This helps non-SAP developers to familiarise themselves with the processes more quickly. Especially the ABAP Development Tools allow developers to manage connections to multiple systems, customize their development experience to their specific needs and increase their productivity. Plugins for the development environment, such as ABAP Cleaner and Code Pal, are only possible in ADT.
 
 The still-existing SAP Developer Workbench (SE80) is obsolete. It was the central tool for ABAP development and available directly in SAP GUI. Its functionality is far surpassed by the ABAP Development Tools in Eclipse, the only remaining part of SE80 that is still used in on-premise systems today is the "New ABAP Debugger" which still has some features that are not matched by the ADT Debugger.
 
 # Resources
-#Article  [SAP Developer Workbench | SAP Help Portal](https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_FOR_SOH_740/bd833c8355f34e96a6e83096b38bf192/cd3965595f154c6895a486b7d006a010.html)
+#Article  [SAP Developer Workbench | SAP Help Portal](https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_FOR_SOH_740/bd833c8355f34e96a6e83096b38bf192/cd3965595f154c6895a486b7d006a010.html)

abap-developer-roadmap/Development Tools/X.1.3 ABAP Development Tools for Visual Studio Code.md

@@ -0,0 +1,14 @@
+#Basic
+Visual Studio Code (VS Code) is a lightweight, extensible code editor that can be adapted to many development scenarios through extensions. It offers familiar editor functions such as syntax highlighting, code completion, integrated terminal support, debugging and Git integration.
+
+ABAP Development Tools for Visual Studio Code brings ABAP development into this editor. It gives developers a local VS Code-based environment for working with ABAP Cloud projects and makes the ABAP toolchain easier to access for developers who already use VS Code in other technology stacks.
+
+Compared to Eclipse with ADT, VS Code focuses on a lean editor experience and a broad extension ecosystem. This can make it easier to get started and to combine ABAP work with other languages or tools in the same workspace.
+
+It is advisable to use the latest version of VS Code and the ABAP Development Tools extension. This ensures that the newest functions and fixes are available.
+
+ADT for VS Code is still at the beginning of its development phase. Currently, connections to an on-premise ABAP system can only be established via SSO.
+
+# Resources
+#Article [ABAP Development Tools for Visual Studio Code is now available on the VS Code Marketplace | SAP Community](https://community.sap.com/t5/technology-blog-posts-by-sap/abap-development-tools-for-visual-studio-code-is-now-available-on-the-vs/ba-p/14402120)
+#Article [ABAP Development Tools for Visual Studio Code | SAP Help Portal](https://help.sap.com/docs/abap-cloud/abap-development-tools-for-visual-studio-code/abap-development-tools-for-visual-studio-code?locale=en-US)

cloud-developer-roadmap/BTP/User Provided Services.md

@@ -0,0 +1,48 @@
+---
+tags:
+  - sap-btp
+  - Basic
+links:
+  - "[[SAP BTP]]"
+  - "[[Service Bindings]]"
+  - "[[Cloud Foundry]]"
+  - "[[cf CLI]]"
+source: https://help.sap.com/docs/btp/sap-business-technology-platform/creating-user-provided-service-instances
+aliases:
+  - ups
+---
+User Provided Services (UPS) are service instances in the [[Cloud Foundry]] environment of [[SAP BTP]] that are created and filled with credentials by the developer or operator. In contrast to managed services from the SAP BTP service marketplace, the platform does not provision the external resource itself. The UPS only stores the connection information that an application needs.
+
+A UPS is used when an application has to consume a service that is not available as a managed service instance in the current space, for example an external API, an existing database, an on-premise endpoint, or a technical service with manually provided credentials. After the UPS has been created, it can be bound to an application like other service instances. The application then receives the credentials through the Cloud Foundry service binding mechanism, usually via the `VCAP_SERVICES` environment variable.
+
+This approach keeps connection data out of the application code and makes it possible to manage endpoint URLs, users, passwords, tokens, or other service-specific properties as part of the platform configuration.
+
+**Example**
+Create a user provided service instance with the [[cf CLI]]:
+
+```sh
+cf create-user-provided-service my-external-api -p '{
+  "url": "https://api.example.com",
+  "clientid": "my-client-id",
+  "clientsecret": "my-client-secret"
+}'
+```
+
+The short form of the command is:
+
+```sh
+cf cups my-external-api -p '{
+  "url": "https://api.example.com",
+  "clientid": "my-client-id",
+  "clientsecret": "my-client-secret"
+}'
+```
+
+Afterwards, the service instance can be bound to an application:
+
+```sh
+cf bind-service my-application my-external-api
+```
+
+**Sources**
+- [SAP Help Portal - Creating User-Provided Service Instances](https://help.sap.com/docs/btp/sap-business-technology-platform/creating-user-provided-service-instances)