AD0-E716 Adobe Commerce Developer with Cloud Add-on

In Adobe Commerce Cloud, connection data for deployed services (such as databases, caches, and other services) can be retrieved using different methods depending on the developer’s access and the tools available.

Using magento-cloud relationships Command :

This CLI command retrieves the connection credentials for the services associated with the environment, such as database and Redis, directly from the command line.

Project Web Interface :

The Project Web Interface provides a dedicated section where developers can access service connection details, making it convenient for those who prefer a graphical interface.

Why Options A and B are Correct :

Both methods are valid and frequently used for accessing connection information. Option C, ece-tools env:config:show services, does not exist. Option D, reading $_ENV[ ' services ' ], would require SSH access and does not provide direct connection details in a user-friendly format.

References :

Adobe Commerce documentation on Accessing Services

The developer should create an extension attribute on the Magento\Sales\Api\Data\OrderInterface interface and an after plugin on the Magento\Sales\Api\OrderRepositoryInterface::get() and Magento\Sales\Api\OrderRepositoryInterface::getList() methods.

The extension attribute will store the custom data. The after plugin will be used to add the custom data to the order object when it is fetched from the API.

Here is the code for the extension attribute and after plugin:

PHP

namespace MyVendor\MyModule\Api\Data;

interface OrderExtensionInterface extends \Magento\Sales\Api\Data\OrderInterface

{

/**

* Get custom data.

*

* @return string|null

*/

public function getCustomData();

/**

* Set custom data.

*

* @param string $customData

* @return $this

*/

public function setCustomData($customData);

}

namespace MyVendor\MyModule\Model;

class OrderRepository extends \Magento\Sales\Api\OrderRepositoryInterface

{

/**

* After get order.

*

* @param \Magento\Sales\Api\OrderRepositoryInterface $subject

* @param \Magento\Sales\Api\Data\OrderInterface $order

* @return \Magento\Sales\Api\Data\OrderInterface

*/

public function afterGetOrder($subject, $order)

{

if ($order instanceof OrderExtensionInterface) {

$order- > setCustomData( ' This is custom data ' );

}

return $order;

}

/**

* After get list.

*

* @param \Magento\Sales\Api\OrderRepositoryInterface $subject

* @param \Magento\Sales\Api\Data\OrderInterface[] $orders

* @return \Magento\Sales\Api\Data\OrderInterface[]

*/

public function afterGetList($subject, $orders)

{

foreach ($orders as $order) {

if ($order instanceof OrderExtensionInterface) {

$order- > setCustomData( ' This is custom data ' );

}

}

return $orders;

}

}

Once the extension attribute and after plugin are created, the custom data will be added to orders fetched from the API.