back-office | V2 of Afup back-office | Web Services library

Product units may be loaded to the database using the data fixtures, like this one that loads default units: https://github.com/oroinc/orocommerce/blob/4.2.1/src/Oro/Bundle/ProductBundle/Migrations/Data/ORM/LoadProductUnitData.php#L47-L52

In addition, you have to provide translations for the new unit, but there are more messages then you specified in the question: https://github.com/oroinc/orocommerce/blob/ad94fe9bd63db28eae7d4a73743a4cada4f49080/src/Oro/Bundle/ProductBundle/Resources/translations/jsmessages.en.yml#L26-L35

The AWS instance id is used as the default admin user password.

Looks like there is a mistake in the documentation. The team will fix it. Thank you!

The root directory is '/var/www/html/commerce'

You can try to insert a new row into a PREFIX_translation table in your database.

Domain should be typed without a dot, like this: EmailsBody.

Unfortunately translations in 1.7 are still a little tricky these days :(

Remember about clearing cache after adding new row into DB.

With awk:

If your pipelines are built on Azure Pipelines, please take a look at:

• Customize Run (build) number
• Customize Release names

Check this blog out for a detailed example. If this doesn't work for you, give this marketplace extension a try.

I have reproduced this using master version 1.15 and and type of service as ‘ClusterIP’. I am able to do look up from the Pod of one service to another. For creating Kubernetes Services in a Google Kubernetes Engine cluster [1] might be helpful.

To see the services: $ kubectl get svc --namespace=default

To access the deployment: $ kubectl exec -it [Pod Name] sh

To lookup: $ nslookup [Service Name]

Every Service defined in the cluster (including the DNS server itself) is assigned a DNS name. By default, a client Pod’s DNS search list will include the Pod’s own namespace and the cluster’s default domain.

“Normal” (not headless) Services are assigned a DNS A record for a name of the form my-svc.my-namespace.svc.cluster-domain.example. This resolves to the cluster IP of the Service.

For “Headless” (without a cluster IP) Services are also assigned a DNS A record for a name.Though this resolves to the set of IPs of the pods selected by the Service.

However, DNS policies can be set on a per-pod basis. Currently Kubernetes supports the following pod-specific DNS policies. These policies are specified in the dnsPolicy field of a Pod Spec [2]:

“Default“: The Pod inherits the name resolution configuration from the node that the pods run on.

“ClusterFirst“: Any DNS query that does not match the configured cluster domain suffix, such as “www.kubernetes.io”, is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured.

“ClusterFirstWithHostNet“: For Pods running with hostNetwork, need to set its DNS policy “ClusterFirstWithHostNet”.

“None“: It allows a Pod to ignore DNS settings from the Kubernetes environment. All DNS settings are supposed to be provided using the dnsConfig field in the Pod Spec.

[1]-https://cloud.google.com/kubernetes-engine/docs/how-to/exposing-apps [2]-https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-config

For administrative type operations, you're better off just running them on your desktop or some other server you control. Cloud Functions is not well suited for long running operations, or things that must just happen once on demand.

Case 1 really should be managed by a standalone program or script that you can monitor by running it on your desktop.

Case 2 can be done a number of ways, such as building your own admin web site. But you might find it easiest to mirror the contents of a document to custom claims using a Firestore trigger. Read this: https://medium.com/firebase-developers/patterns-for-security-with-firebase-supercharged-custom-claims-with-firestore-and-cloud-functions-bb8f46b24e11

Oro commerce installation (v. 4.0).

You are using a 4.0 version, but browse documentation for 4.1 version. In 4.0 there was no such an option and API was always enabled. There is no documentation for the 4.0 version as it's unsupported preview version. Consider to upgrade, or if it's a new installation, better to reinstall the plain CRM

The composer link is wrong

Yes, you are right, we'll fix it, thanks for noticing. For now, you can install 4.1 version of OroCRM by following the documentation on a website, except the composer application name, please replace it to the crm-application.

OAuth Pb

Please install 4.1 version of a CRM application and start over. If it will still not work, look for error messages in a var/logs folder.